Multimedia messaging service communication using a two way push connection

ABSTRACT

Systems and methods for generating and transmitting multimedia messaging service (MMS) messages are disclosed. In some implementations, a mobile device presents, at a touchscreen, a visual user interface. The visual user interface includes multiple thumbnails and multiple contact blocks. Each thumbnail identifies a file. Each contact block identifies a contact having a messaging address. The mobile device receives, via the touchscreen, a selection of a first thumbnail from the multiple thumbnails. The mobile device receives, via the touchscreen, an indication of dragging the first thumbnail across the visual user interface to a first contact block. The mobile device transmits, responsive to the dragging of the first thumbnail to the first contact block, the file identified in the thumbnail to the messaging address of the contact identified in the first contact block.

BACKGROUND

Oftentimes, users of mobile devices send multimedia messaging service(MMS) messages to one another to share images or videos. However,existing MMS messaging technologies suffer from many drawbacks. At themobile device, the application for sending MMS messages is oftentimesunintuitive, requiring the user to learn complex schemes for selectingan image or a video, selecting a contact, and having the image or thevideo transmitted to the contact. At the server, the application forsending MMS messages may only be able to handle small file sizes or mayexperience significant delay due to a large number of large files beingtransmitted and “bottleneck” at the server, resulting in slowtransmission of messages and reduction of file sizes of images or videosbeing transmitted. As the foregoing illustrates, new approaches for MMSapplications at mobile devices and MMS transmission at servers may bedesirable.

BRIEF DESCRIPTION OF THE DRAWINGS

The drawing figures depict one or more implementations in accord withthe present teachings, by way of example only, not by way of limitation.In the figures, like reference numerals refer to the same or similarelements.

FIG. 1 illustrates an exemplary mobile device for transmitting amultimedia messaging service message;

FIG. 2 is a high-level functional block diagram of an exemplary mobiledevice for transmitting a multimedia messaging service message;

FIG. 3 is a flow chart illustrating an exemplary process for generatinga multimedia messaging service message at a mobile device;

FIG. 4 is a high-level functional block diagram of an exemplarymultimedia messaging service server;

FIG. 5 is a flow chart illustrating an exemplary process fortransmitting a multimedia messaging service message;

FIG. 6 is a high-level functional block diagram of an example of asystem of networks/devices that provide various communications formobile stations, using which multimedia messaging service communicationmay be implemented;

FIG. 7 is a high-level functional block diagram of an exemplarynon-touch type mobile device which may be involved in multimediamessaging service communication;

FIG. 8 is a high-level functional block diagram of an exemplary touchscreen type mobile device which may be involved in multimedia messagingservice communication;

FIG. 9 illustrates a first exemplary system in which push communicationmay be implemented;

FIG. 10 illustrates a second exemplary system in which pushcommunication may be implemented; and

FIG. 11 is a data flow diagram of transmitting a multimedia messagingservice message using push communication.

DETAILED DESCRIPTION

In the following detailed description, numerous specific details are setforth by way of examples in order to provide a thorough understanding ofthe relevant teachings. However, it should be apparent that the presentteachings may be practiced without such details. In other instances,well known methods, procedures, components, and/or circuitry have beendescribed at a relatively high-level, without detail, in order to avoidunnecessarily obscuring aspects of the present teachings.

The subject technology provides techniques for multimedia messagingservice (MMS) communication. Some aspects of the subject technology aredirected to an MMS messaging application at a mobile device, which mayinclude a touchscreen. Some aspects of the subject technology aredirected to server-side MMS transmission techniques. Advantageously,according to some implementations of the subject technology, MMScommunication may be more intuitive for mobile device users and moreuser-friendly than previously available alternative MMS technologies. Atthe server side, the MMS communication technology may be able totransmit larger data files and provide users with a real-timeconfirmation that their MMS messages have been successfully transmitted.Additionally, user privacy may be protected by storing less informationabout users at the server. Specifically an MMS message file may bestored at the server before the file is transmitted to the recipient,but not after successful receipt of the file by the recipient.

FIG. 1 illustrates an exemplary mobile device 100 for transmitting anMMS message. As illustrated, the mobile device 100 is a mobile phone.However, the mobile device may be any other device configured to receiveMMS messages, for example, a tablet computer, a digital music player, ora laptop or desktop computer including a MMS application associated witha mobile telephony account. As shown, the mobile device 100 has atouchscreen that presents a visual user interface 105. The mobile device100 may be executing an MMS application, which presents the visual userinterface 105 at the touchscreen.

The visual user interface 105 presents thumbnails 110.a-110.1 ofmultiple images from an image library of the mobile device. While thethumbnails 110.a-110.1 are illustrated as corresponding to images, eachthumbnail 110 may correspond to any type of file, for example, a videofile. Also, any number of thumbnails, not necessarily 12, may bepresented in the visual user interface 105. If there are more thumbnailsavailable than are presented in the visual user interface 105, the usermay scroll through the thumbnails using scroll buttons 120.a and 120.bor by swiping to the left or to the right (or, alternatively, up ordown).

The visual user interface 105 also presents contact blocks 115.a-115.c.Each contact block identifies a contact (e.g., Emily, Fred, or Mom)associated with an MMS address (e.g., a mobile device number (MDN)) towhich MMS message(s) may be sent. Any number of contact blocks, notnecessarily three, may be presented in the visual user interface 105. Ifthere are more contacts available than are presented in the visual userinterface 105, the user may scroll through the contacts using the scrollbuttons 125.a and 125.b or by swiping to the left or to the right (or,alternatively, up or down).

As shown, the thumbnails 110.a-110.1 and the contact blocks 115.a-115.care presented adjacent to opposite edges of the visual user interface105. Specifically, the thumbnails 110.a-110.1 are presented adjacent tothe top edge 140 and the contact blocks 115 a-115.c are presentedadjacent to the bottom edge 145. However, in alternativeimplementations, the thumbnails 110.a-110.1 and the contact blocks 115a-115.c may be presented adjacent to any edge or any two opposite edges.

In order to send an MMS message, a user may select a thumbnail of a filethe user desires to send via MMS and drag and drop the thumbnail to thecontact block of the contact to whom the file is to be sent. Forexample, as shown, the user has selected thumbnail 110.h by placinghis/her finger 130 on thumbnail 110.h. The user then moved his/herfinger 130 along path 135 to drag and drop the selected thumbnail 110.hto contact 115.a, named Emily. The file associated with the thumbnail110.h may be sent to the MMS messaging address (e.g., MDN) associatedwith Emily using MMS. The file may be sent to the MMS messaging addressassociated with Emily as soon as the user drops the selected thumbnail110.h on the contact block 115.a corresponding to Emily. Alternatively,the user may be presented with an interface for adding text to the MMSmessage to Emily. The interface for adding text to the MMS message maybe presented on the visual user interface 105 of the mobile device 100and may include, for example, a block into which the user may type textvia keyboard presented on the touchscreen.

Advantageously, the interface presented in FIG. 1 allows a user toeasily select a file to transmit via MMS message and a contact to whomthe file should be transmitted. As shown, the files/images are close tothe top of the device and the contacts are close to the bottom of thedevice due to the fact that users can more quickly move their fingersfrom top to bottom than from bottom to top, regardless of whether theyare right-handed or left-handed. An alternative design may havefiles/images at the left and contacts at the right, due to theconvenience for right-handed users of moving their fingers from left toright. However, this alternative design may be inconvenient forleft-handed users. In some examples, a user may select an edge next towhich the files/images are placed and an opposite edge next to which thecontacts are placed. In these examples, the user may make the selectionbased on what is easier for the user and based on whether the user isright-handed or left-handed.

FIG. 2 is a high-level functional block diagram of an exemplary mobiledevice 200 for transmitting an MMS message. The mobile device 200 maycorrespond to the mobile device 100 illustrated in FIG. 1. As shown, themobile device 200 includes a processor 205, a network interface 210, atouchscreen 215, and a memory 220. The processor 205 executesinstructions stored in a machine-readable medium, for example, thememory 220. While a single processor 205 is illustrated, the mobiledevice 200 may include multiple processors, which may be arranged intoprocessing units, such as a central processing unit (CPU) or a graphicsprocessing unit (GPU). The network interface 210 allows the mobiledevice 200 to access a network, for example, a cellular network fortransmitting MMS messages, transmitting text messages, making calls,accessing cellular data, etc., or a WiFi network. The touchscreen 215displays a graphical user interface (GUI), for example, the visual userinterface 105 of FIG. 1, and receives touch input for processing by theprocessor 205 based on instructions stored in the memory 220. The memory220 stores data and/or instructions. As shown, the memory 220 storescontacts 225.1-m, files 230.1-n, a touchscreen driver 235, a MMScomposition module 240, and a MMS transmission client module 245.

The contacts 225.1-225.m include a contact list of the user of themobile device 200. Each contact 225.p (where p is a number between 1 andm) may be associated with one or more of a name, a telephone number, anemail address, a postal address, a fax number, social networkinginformation, etc. The files 230.1-230.n include files stored locally atthe mobile device 200. Each file 230.q (where q is a number between 1and n) may include a photograph, a video, an audio file, a wordprocessing document, a spreadsheet, a presentation file, etc.

The touchscreen driver 235 includes instructions which, when executed bythe processor 205, cause the processor 205 to provide visual output atthe touchscreen 215 and/or receive touch input via the touchscreen 215.The type of visual output and/or the responses by the mobile device 200to the touch input may be determined based on programmed instructionsstored in the memory 220, for example, instructions in the MMScomposition module 240, as discussed below. In some examples, the visualoutput corresponds to the visual user interface 105 of FIG. 1, and thetouch input corresponds to the user touching the touchscreen 215 withhis/her finger 130 and moving his/her finger 130 along path 135 on thetouchscreen 215.

The MMS composition module 240 includes instructions which, whenexecuted by the processor 205, cause the processor 205 to present, atthe touchscreen 215 and using the touchscreen driver 235, a visual userinterface that includes thumbnails corresponding to some or all of thefiles 230.1-230.n and contact blocks corresponding to some or all of thecontacts 225.1-225.m. The processor 205 receives, via the touchscreen215 and using the touchscreen driver 235, a selection of a firstthumbnail from among the thumbnails. The processor 205 receives, via thetouchscreen 215 and using the touchscreen driver 235, an indication ofdragging (e.g., using a finger or a stylus) the first thumbnail acrossthe visual user interface on the touchscreen 215 to a first contactblock from among the contact blocks. The processor 205 then invokes theMMS transmission client module 245. The MMS transmission client module245 includes instructions which, when executed by the processor 205,cause the processor 205 to transmit the file 230.q (where q is a numberbetween 1 and n) identified in the thumbnail to the MMS messagingaddress (e.g., MDN) of the contact 225.p identified in the first contactblock.

FIG. 3 is a flow chart illustrating an exemplary process 300 forgenerating an MMS message at a mobile device. The process 300 begins atstep 310, where a mobile device (e.g., mobile device 100 or 200)presents at the touchscreen (e.g., touchscreen 215) a visual userinterface (e.g., visual user interface 105). The visual user interfaceincludes multiple thumbnails (e.g., thumbnails 110.a-110.1) and multiplecontact blocks (e.g., contact blocks 115.a-115.c). Each thumbnailidentifies a file (e.g., one of the files 230.1-230.n). Each contactblock identifies a contact (e.g.., one of the contacts 225.1-225.m)having a MMS messaging address. For example, each contact block mayinclude a name of the identified contact. The name may be a first name,a last name, or a combination of the first name and the last name.

In one example, the contact blocks are presented next to a top edge ofthe visual user interface, and the thumbnails are presented next to abottom edge of the visual user interface. Alternatively, the contactblocks and the thumbnails may be presented adjacent to the right edgeand the left edge, respectively, of the visual user interface. In otherimplementations, the contact blocks and the thumbnails may be presentedanywhere on the visual user interface. In some examples, the contactblocks and the thumbnails may be interspersed with one another.

In one example, the contact blocks correspond to all of the contacts ofthe user and are arranged alphabetically. If there are more contactsthan can fit in the visual user interface, the user may be able toscroll through the contacts, for example, by swiping the contacts to theleft, to the right, up or down, by using arrows for scrolling, or byusing a scroll bar and a scroll thumb. In one example, the contactblocks correspond to the favorite contacts of the user, and the user mayswipe to view other, non-favorite contacts. In yet another example, thecontact blocks correspond to the contacts of the user to whom the userhas sent the largest number of MMS messages during the last thresholdtime period (e.g., last week, last month, last three months, etc.). Thelength of the threshold time period may be determined based on howfrequently the user sends MMS messages. For example, for a user whosends an average of 10 MMS messages per day, the threshold time periodmay be one week. For a user who sends an average of 1 MMS message perweek, the threshold time period may be one per year.

In some examples, the displayed contact blocks may correspond to themost frequent contacts of the user. The frequent contacts of the usermay include contacts with whom the user most frequently communicatesusing a mobile device-based communication. The mobile device-basedcommunication may include, for example, cellular phone calls, textmessages, MMS messages, email messages sent from the mobile device, orsocial network-based contact using the mobile device. The mobile devicemay determine the contacts with whom the user most frequentlycommunicates based on a number of times that the user has communicatedwith the contact during a predetermined time period (e.g., last week,last two weeks, last two months, etc.) The length of the predeterminedtime period may be determined based on how frequently the usercommunicates using the mobile device. For example, a user who uses themobile device to communicate 40-50 times per day, on average, may have apredetermined time period of one day. A user who uses the mobile deviceto communicate once or only a few times per day, on average, may have apredetermined time period of two months.

In step 320, the mobile device receives, via the touchscreen, aselection of a first thumbnail from the multiple thumbnails. Forexample, the user may touch the touchscreen, at a position correspondingto first thumbnail, using a finger or a stylus. In step 330, the mobiledevice receives, via the touchscreen, an indication of dragging thefirst thumbnail across the visual user interface to a first contactblock from among the multiple contact blocks. In step 340, the mobiledevice transmits, via a messaging server and responsive to the draggingof the first thumbnail to the first contact block, the file identifiedin the thumbnail to the MMS messaging address of the contact identifiedin the first contact block. A push connection is established between themobile device and the messaging server, and between the messaging serverand a device associated with the messaging address. As a result of thistwo-way push connection, the file may be transmitted from the mobiledevice to the device associated with the messaging address in real-time.After step 340, the process 300 ends.

Aspects of the subject technology related to a mobile device arediscussed, for example, in conjunction with FIGS. 1-3. Aspects of thesubject technology related to a MMS server are discussed, for example,in conjunction with FIGS. 4 and 5. The mobile device aspects and the MMSserver aspects of the subject technology may be implemented togetherwith one another or independently of and separately from one another.

According to some implementations, an MMS server receives, from a sendermobile device, a message including a recipient device address (e.g., anMDN, such as +1-917-555-1234) and a file (e.g., an image file, a videofile, or any other file). The message may be pushed to the MMS serverfrom the sender mobile device. The MMS server attempts to transmit thefile to a recipient mobile device associated with the recipient deviceaddress. In a case where the attempt to transmit the file is successful,the MMS server receives an acknowledgement that the file was received atthe mobile device. The MMS server in response to receiving theacknowledgement deletes the file from the memory of the MMS server. TheMMS server also in response to receiving the acknowledgement transmitsto the sender mobile device an indication that the file is successfullytransmitted to the recipient mobile device.

In a case where the attempt to transmit the file is unsuccessful, theMMS server reattempts to transmit the file to the recipient mobiledevice. The reattempt may occur a certain amount of time (e.g., 10minutes, 1 hour, 3 hours, etc.) after the previous attempt, depending onthe load of the MMS server. The MMS server retains the file in a memoryof the MMS server until the file is successfully transmitted to therecipient mobile device, a request to cancel the attempt to transmit thefile is received from the sender mobile device, a threshold time period(e.g., three hours or six hours) passes after receipt of the messagefrom the sender mobile device, or a threshold number (e.g., five or ten)of attempts to transmit the MMS message to the recipient have been made.The threshold time period or the threshold number of attempts may bedetermined based on the identity of the mobile device transmitting theMMS message, the type of file being transmitted, or the size of thefile. For example, the threshold time period or the threshold number ofattempts may be larger if the mobile device is a smartphone rather thana non-smart phone, if the type of file is an image rather than a video,or if the size of the file is smaller. In some cases, the MMS server maydetermine a failure reason why the attempt to transmit the file isunsuccessful. The MMS server may transmit to the sender mobile device anindication of the failure reason, so that the user of the sender mobiledevice may decide whether to reattempt to send the message at adifferent time or to attempt to send the message to another contact. Forexample, a father may attempt to send a photograph of his child playingwith a toy to his sister. The MMS server may determine that the sister'smobile device is offline and inform the father of this determination. Inresponse, the father may decide to resend the message hour(s) or day(s)later when the sister is likely to be online. Alternatively, the fathermay decide to resend the message to the sister's husband, who the fatherknows to be online and in the same geographic location as the sister.Alternatively, the father may decide to forego sending the photograph tothe sister as it is not important or urgent. Exemplary failure reasonsmay include: the recipient mobile device is offline, the recipientmobile device is busy, or the recipient mobile device lacks memory tostore the file. The MMS server may determine that the recipient mobiledevice is offline by attempting to contact the recipient mobile deviceand failing to receive a response. The MMS server may determine that therecipient mobile device is busy by communicating with other server(s)belonging to the mobile operator (e.g., a mobile data server, a voicecalling server, etc.) and determining that the other servers areproviding data to the mobile device. The MMS server may determine thatthe recipient mobile device lacks memory to store the file by attemptingto transmit the file to the mobile device and receiving a “lack ofmemory error” response from the mobile device.

FIG. 4 is a high-level functional block diagram of an exemplary MMSserver 400. While the MMS server 400 is illustrated as a single machine,the MMS server 400 may include a single machine or multiple machines. Asshown, the MMS server 400 includes a processor 405, a network interface410, and a memory 415. The processor 405 executes instructions stored ina machine-readable medium, for example, the memory 415. While a singleprocessor 405 is illustrated, the mobile device 200 may include multipleprocessors, which may be arranged into processing units, such as a CPUor a GPU. The network interface 410 allows the MMS server 400 to accessa network, for example, a cellular network for transmitting MMSmessages, transmitting text messages, making calls, accessing cellulardata, etc., or a WiFi network.

The memory 415 stores data and/or instructions. As shown, the memory 415includes a long-term memory 420 and a short-term memory 425. Thelong-term memory 420 may include data and/or instructions that arerarely removed and may be occasionally (e.g., once every month or year)modified, for example, via software updates. The short-term memory 425includes data and/or instructions that are erased or cleared frequently,for example, after a MMS message is successfully received at a recipientdevice. Data may be stored in the short-term memory 425 for 10 seconds,1 minute, 5 minutes, 1 hour, etc.

As illustrated, the short-term memory 425 stores a MMS message 435 thatis being processed by the MMS server 400. While a single MMS message 435is illustrated, the short-term memory 425 may store multiple MMSmessages which are simultaneously being processed by the MMS server 400.The MMS message 435 includes a recipient address 440, a file 445, andtext 450. In some cases, the MMS message 435 may lack text 450. Afterthe MMS message 435 is successfully transmitted to a device associatedwith the recipient address 440, the MMS message 435, including therecipient address 440, the file 445, and the text 450, may be removedfrom the short-term memory 425 and stored only at a device of the senderand the device associated with the recipient address 440.

As illustrated, the long-term memory 420 stores an MMS transmissionserver module 430. The MMS transmission server module 430 may includecode which, when executed by the processor 405, causes the processor 405to receive the MMS message 435 from a sender device (e.g., mobile device100 or 200) and to transmit the MMS message 435 to a device associatedwith the recipient address 440. After the MMS message 435 is received atthe device associated with the recipient address 440, the MMS message435, including the attached file 445, may be removed from the short-termmemory 425. One example of the operation of the MMS transmission servermodule 430 is described in conjunction with FIG. 5.

FIG. 5 is a flow chart illustrating an exemplary process 500 fortransmitting an MMS message. The process 500 begins at step 510, where aserver (e.g., MMS server 400, executing the MMS transmission servermodule 430) receives, from a sender mobile device (e.g., mobile device100 or 200), a message (e.g., MMS message 435) including a recipientdevice address (e.g., recipient address 440) and a file (e.g., file445). The message may, in some cases, also include text (e.g., text450). The file may be an image file or a video file.

In step 520, the server attempts to transmit the file to a recipientmobile device associated with the recipient device address. For example,the server may push the file to the recipient mobile device in real-timeafter receiving, from the sender mobile device, the message includingthe recipient device address and the file. The recipient device addressmay be an MDN, and the recipient mobile device may be a mobile devicehaving the MDN. Alternatively, the recipient device address may be anemail address or a social networking account identifier, and therecipient device may be a mobile device associated with the emailaddress or the social networking account identifier.

In step 530, the process 500 branches based on whether the attempt totransmit the file to the recipient mobile device associated with therecipient device address was successful. If the attempt to transmit thefile to the recipient mobile device associated with the recipient deviceaddress was successful, the process 500 continues to step 540. If theattempt to transmit the file to the recipient mobile device associatedwith the recipient device address is unsuccessful, the process 500continues to step 570.

In step 540, if the attempt to transmit the file to the recipient mobiledevice was successful, the server receives, from the recipient mobiledevice, an acknowledgement that the MMS message, including the file, wasreceived at the recipient mobile device. In step 550, the server deletesthe file from a local memory (e.g., memory 415) of the server. In step560, the server transmits, to the sender mobile device, an indicationthat the file is successfully transmitted to the recipient mobiledevice. After step 560, the process 500 ends.

In step 570, if the attempt to transmit the file to the recipient mobiledevice is unsuccessful, the server reattempts to transmit the file tothe recipient mobile device. The server may transit, to the sendermobile device, an indication that the attempt to transmit the file isunsuccessful. In some cases, the server may determine a failure reasonwhy the attempt to transmit the file is unsuccessful. For example, theserver may determine that the recipient mobile device is offline, thatthe recipient mobile device is busy, or that the recipient mobile devicelacks memory to store the attached file. The server may transmit to thesender mobile device an indication of the failure reason.

In step 580, the server retains the file in the local memory of theserver until the file is successfully transmitted to the recipientmobile device. Upon successful transmission of the file to the recipientmobile device, the file is deleted from the local memory of the server.After step 580, the process 500 ends.

As described above in conjunction with FIG. 5, the server retains thefile in the local memory of the server until the file is successfullytransmitted to the recipient mobile device. However, in alternativeimplementations, the server may remove the message, including the fileand the recipient device address, from its local memory under differentcircumstances. For example, the server may remove the message from itslocal memory upon receiving, from the sender mobile device, a request tocancel the attempt to transmit the file. The server may remove themessage from its local memory when a waiting time period passes afterreceipt of the message from the sender mobile device. The waiting timeperiod may be programmed into the server and may be, for example, 6hours, 12 hours, or 24 hours. The waiting period may vary depending onan amount of free memory at the server or an amount of traffic on thenetwork. If the network has low traffic or the server has a large amountof free memory, the waiting period may be longer. Alternatively, if thenetwork has high traffic or the server has a small amount of freememory, the waiting period may be shorter.

FIG. 6 illustrates a system 10 offering a variety of mobilecommunication services. The mobile communication services include MMSservices, offered through the MMS server 400, as described herein. Theexample shows simply two mobile stations (MSs) 13 a and 13 b as well asa mobile communication network 15. The mobile stations 13 a and 13 b areexamples of mobile stations. The network 15 provides mobile wirelesscommunications services to those stations as well as to other mobilestations (not shown), for example, via a number of base stations (BSs)17. Each of the mobile stations 13 a and 13 b may correspond to a mobiledevice transmitting a MMS message, such as the mobile device 100 or 200,or a mobile device receiving a MMS message. The present techniques maybe implemented in or used in any of a variety of available mobilenetworks 15, and the drawing shows only a very simplified example of afew relevant elements of the network 15 for purposes of discussion here.

The wireless mobile communication network 15 might be implemented as anetwork conforming to the code division multiple access (CDMA) IS-95standard, the 3rd Generation Partnership Project 2 (3GPP2) wireless IPnetwork standard or the Evolution Data Optimized (EVDO) standard, theGlobal System for Mobile (GSM) communication standard, a time divisionmultiple access (TDMA) standard, the Universal Mobile TelecommunicationsSystem (UMTS) standard, the LTE standard belonging to 3GPP or otherstandards used for public mobile wireless communications. The mobilestations 13 may be capable of voice telephone communications through thenetwork 15. Alternatively or additionally, the mobile stations 13a and13 b may be capable of data communications through the particular typeof network 15 (and the users thereof typically will have subscribed todata service through the network).

The network 15 allows users of the mobile stations such as 13 a and 13 b(and other mobile stations not shown) to initiate and receive telephonecalls to each other as well as through the public switched telephonenetwork or “PSTN” 19 and telephone stations 21 connected to the PSTN.The network 15 typically offers a variety of data services via theInternet 23, such as downloads, web browsing, email, etc. The network 15offers MMS services to the users of the mobile stations, for example 13a and 13 b, through the MMS server 400, which is connected to thenetwork 15. By way of example, the drawing shows a laptop PC type userterminal 27 as well as a server 25 connected to the Internet 23; and thedata services for the mobile stations 13 via the Internet 23 may be withdevices like those shown at 25 and 27 as well as with a variety of othertypes of devices or systems capable of data communications throughvarious interconnected networks.

Mobile stations 13 can take the form of portable handsets, smart-phonesor personal digital assistants, although they may be implemented inother form factors. Program applications can be configured to execute onmany different types of mobile stations 13. For example, a mobilestation application can be written to execute on a binary runtimeenvironment for mobile (BREW-based) mobile station, a Windows Mobilebased mobile station, Android, I-Phone, Java Mobile, or RIM based mobilestation such as a BlackBerry or the like. Some of these types of devicescan employ a multi-tasking operating system.

The mobile communication network 10 can be implemented by a number ofinterconnected networks. Hence, the overall network 10 may include anumber of radio access networks (RANs), as well as regional groundnetworks interconnecting a number of RANs and a wide area network (WAN)interconnecting the regional ground networks to core network elements. Aregional portion of the network 10, such as that serving mobile stations13, can include one or more RANs and a regional circuit and/or packetswitched network and associated signaling network facilities.

Physical elements of a RAN operated by one of the mobile serviceproviders or carriers, include a number of base stations represented inthe example by the base stations (BSs) 17. Although not separatelyshown, such a base station 17 can include a base transceiver system(BTS), which can communicate via an antennae system at the site of basestation and over the airlink with one or more of the mobile stations 13,when the mobile stations are within range. Each base station can includea BTS coupled to several antennae mounted on a radio tower within acoverage area often referred to as a “cell.” The BTS is the part of theradio network that sends and receives RF signals to/from the mobilestations 13 that are served by the base station 17.

The radio access networks can also include a traffic network representedgenerally by the cloud at 15, which carries the user communications anddata for the mobile stations 13 between the base stations 17 and otherelements with or through which the mobile stations communicate. Thenetwork can also include other elements that support functionality otherthan device-to-device media transfer services such as messaging servicemessages and voice communications. Specific elements of the network 15for carrying the voice and data traffic and for controlling variousaspects of the calls or sessions through the network 15 are omitted hereform simplicity. It will be understood that the various network elementscan communicate with each other and other aspects of the mobilecommunications network 10 and other networks (e.g., the public switchedtelephone network (PSTN) and the Internet) either directly orindirectly.

The carrier will also operate a number of systems that provide ancillaryfunctions in support of the communications services and/or applicationservices provided through the network 10, and those elements communicatewith other nodes or elements of the network 10 via one or more privateIP type packet data networks 29 (sometimes referred to as an Intranet),i.e., a private networks. Generally, such systems are part of orconnected for communication via the private network 29. A person skilledin the art, however, would recognize that systems outside of the privatenetwork could serve the same functions as well. Examples of suchsystems, in this case operated by the network service provider as partof the overall network 10, which communicate through the intranet typenetwork 29, include one or more application servers 31 and a relatedauthentication server 33 for the application service of server 31.

A mobile station 13 communicates over the air with a base station 17 andthrough the traffic network 15 for various voice and datacommunications, e.g. through the Internet 23 with a server 25 and/orwith application servers 31. Services offered by the mobile servicecarrier may be hosted on a carrier operated application server 31, forcommunication via the networks 15 and 29. Server such as 25 and 31 mayprovide any of a variety of common application or service functions insupport of or in addition to an application program running on themobile station 13. For a given service, an application program withinthe mobile station may be considered as a ‘client’ and the programmingat 25 or 31 may be considered as the ‘server’ application for theparticular service.

To insure that the application service offered by server 31 is availableto only authorized devices/users, the provider of the applicationservice also deploys an authentication server 33. The authenticationserver 33 could be a separate physical server as shown, orauthentication server 33 could be implemented as another program modulerunning on the same hardware platform as the server application 31.Essentially, when the server application (server 31 in our example)receives a service request from a client application on a mobile station13, the server application provides appropriate information to theauthentication server 33 to allow server application 33 to authenticatethe mobile station 13 as outlined herein. Upon successfulauthentication, the server 33 informs the server application 31, whichin turn provides access to the service via data communication throughthe various communication elements (e.g. 29, 15 and 17) of the network10.

The subject technology may be implemented in conjunction with touchscreen type mobile stations as well as to non-touch type mobilestations. Hence, our simple example shows the mobile station (MS) 13 aas a non-touch type mobile station and shows the mobile station (MS) 13as a touch screen type mobile station. Some implementation may involveat least some execution of programming in the mobile stations as well asimplementation of user input/output functions and data communicationsthrough the network 15, from the mobile stations. Those skilled in theart presumably are familiar with the structure, programming andoperations of the various types of mobile stations. However, for thesake of completeness two types of mobile stations are described belowwith respect to FIGS. 7 and 8.

The mobile stations of FIGS. 7 and 8 may correspond to the mobile device100 or 200 or to a mobile device receiving an MMS message. FIG. 7illustrates exemplary non-touch type mobile device. FIG. 8 illustratesan exemplary touch screen type mobile device.

As shown by the above discussion, functions relating to MMScommunication may be implemented on computers connected for datacommunication via the components of a packet data network, as shown inFIG. 6. For example, the mobile device 100 or 200 may correspond to themobile station 13 a or the mobile station 13 b. The MMS server 400 maycorrespond to the application servers 31. Although special purposedevices may be used, such devices also may be implemented using one ormore hardware platforms intended to represent a general class of dataprocessing device commonly used to run “server” programming so as toimplement the functions discussed above, albeit with an appropriatenetwork connection for data communication.

FIG. 7 provides a block diagram illustration of an exemplary non-touchtype mobile device 13 a, which may correspond to the mobile device 13.Although the mobile device 13 a may be a smart-phone or may beincorporated into another device, such as a personal digital assistant(PDA) or the like, for discussion purposes, the illustration shows themobile device 13 a is in the form of a handset. The handset embodimentof the mobile device 13 a functions as a normal digital wirelesstelephone station. For that function, the mobile device 13 a includes amicrophone 702 for audio signal input and a speaker 704 for audio signaloutput. The microphone 702 and speaker 704 connect to voice coding anddecoding circuitry (vocoder) 706. For a voice telephone call, forexample, the vocoder 706 provides two-way conversion between analogaudio signals representing speech or other audio and digital samples ata compressed bit rate compatible with the digital protocol of wirelesstelephone network communications or voice over packet (InternetProtocol) communications.

For digital wireless communications, the mobile device 13 a alsoincludes at least one digital transceiver (XCVR) 708. The mobile device13 a may be configured for digital wireless communications using one ormore of the common network technology types. The concepts discussed hereencompass embodiments of the mobile device utilizing any digitaltransceivers that conform to current or future developed digitalwireless communication standards. The mobile device may also be capableof analog operation via a legacy network technology.

The transceiver 708 provides two-way wireless communication ofinformation, such as vocoded speech samples and/or digital information,in accordance with the technology of the network 165. The transceiver708 also sends and receives a variety of signaling messages in supportof the various voice and data services provided via the mobile device 13a and the communication network. Each transceiver 708 connects throughRF send and receive amplifiers (not separately shown) to an antenna 710.The transceiver may also support various types of mobile messagingservices, such as short message service (SMS), enhanced messagingservice (EMS) and/or multimedia messaging service (MMS).

The mobile device 13 a includes a display 718 for displaying messages,menus or the like, call related information dialed by the user, callingparty numbers, etc. A keypad 720 enables dialing digits for voice and/ordata calls as well as generating selection inputs, for example, as maybe keyed-in by the user based on a displayed menu or as a cursor controland selection of a highlighted item on a displayed screen. The display718 and keypad 720 are the physical elements providing a textual orgraphical user interface. Various combinations of the keypad 720,display 718, microphone 702 and speaker 704 may be used as the physicalinput output elements of the graphical user interface (GUI), formultimedia (e.g., audio and/or video) communications. Of course otheruser interface elements may be used, such as a trackball, as in sometypes of PDAs or smart phones.

In addition to normal telephone and data communication relatedinput/output (including message input and message display functions),the user interface elements also may be used for display of menus andother information to the user and user input of selections.

A microprocessor 712 serves as a programmable controller for the mobiledevice 13 a, in that it controls all operations of the mobile device 13a in accordance with programming that it executes, for all normaloperations, including those under consideration here. In the example,the mobile device 13 a includes flash type program memory 714, forstorage of various “software” or “firmware” program routines and mobileconfiguration settings, such as mobile directory number (MDN) and/ormobile identification number (MIN), etc. The flash type program memory714 stores programed instructions, including those described herein. Themobile device 13 a may include a non-volatile random access memory (RAM)716 for a working data processing memory. Of course, other storagedevices or configurations may be added to or substituted for those inthe example. In a present implementation, the flash type program memory714 stores firmware such as a boot routine, device driver software, anoperating system, call processing software and vocoder control software,and any of a wide variety of other applications, such as client browsersoftware and short message service software. The memories 714, 716 alsostore various data, such as telephone numbers and server addresses,downloaded data such as multimedia content, and various data input bythe user. Programming stored in the flash type program memory 714,sometimes referred to as “firmware,” is loaded into and executed by themicroprocessor 712.

As outlined above, the mobile device 13 a includes a processor, andprogramming stored in the flash memory 714 configures the processor sothat the mobile device is capable of performing various desiredfunctions, including those described herein.

For purposes of such a discussion, FIG. 8 provides a block diagramillustration of an exemplary touch screen type mobile device 13 b.Although possible configured somewhat differently, at least logically, anumber of the elements of the exemplary touch screen type mobile device13 b are similar to the elements of mobile device 13 a, and areidentified by like reference numbers in FIG. 8. For example, the touchscreen type mobile device 13 b includes a microphone 702, speaker 704and vocoder 706, for audio input and output functions, much like in theearlier example. The mobile device 13 b also includes at least onedigital transceiver (XCVR) 708, for digital wireless communications,although the mobile device 13 b may include an additional digital oranalog transceiver. The concepts discussed here encompass embodiments ofthe mobile device 13 b utilizing any digital transceivers that conformto current or future developed digital wireless communication standards.As in the mobile device 13 a, the transceiver 708 provides two-waywireless communication of information, such as vocoded speech samplesand/or digital information, in accordance with the technology of thenetwork 165. The transceiver 708 also sends and receives a variety ofsignaling messages in support of the various voice and data servicesprovided via the mobile device 13 b and the network 165. Eachtransceiver 708 connects through RF send and receive amplifiers (notseparately shown) to an antenna 710. The transceiver may also supportvarious types of mobile messaging services, such as short messageservice (SMS), enhanced messaging service (EMS) and/or multimediamessaging service (MMS).

As in the example of the mobile device 13a, a microprocessor 712 servesas a programmable controller for the mobile device 13b, in that itcontrols all operations of the mobile device 13 b in accordance withprogramming that it executes, for all normal operations, and foroperations described herein. In the example, the mobile device 13 bincludes flash type program memory 714, for storage of various programroutines and mobile configuration settings. The mobile device 13 b mayalso include a non-volatile random access memory (RAM) 716 for a workingdata processing memory. Of course, other storage devices orconfigurations may be added to or substituted for those in the example.Hence, outlined above, the mobile device 13 b includes a processor, andprogramming stored in the flash memory 714 configures the processor sothat the mobile device is capable of performing various desiredfunctions, including the functions described herein.

In the example of FIG. 8, the user interface elements included a displayand a keypad. The mobile device 13 b may have a limited number of key(s)730, but the user interface functions of the display and keypad arereplaced by a touchscreen display arrangement. At a high level, atouchscreen display is a device that displays information to a user andcan detect occurrence and location of a touch on the area of thedisplay. The touch may be an actual touch of the display device with afinger, stylus or other object, although at least some touchscreens canalso sense when the object is in close proximity to the screen. Use of atouchscreen display as part of the user interface enables a user tointeract directly with the information presented on the display.

Hence, the exemplary mobile device 13 b includes a display 722, whichthe microprocessor 712 controls via a display driver 724, to presentvisible outputs to the device user. The mobile device 13 b also includesa touch/position sensor 726. The sensor 726 is relatively transparent,so that the user may view the information presented on the display 722.A sense circuit 728 sensing signals from elements of the touch/positionsensor 726 and detects occurrence and position of each touch of thescreen formed by the display 722 and sensor 726. The sense circuit 728provides touch position information to the microprocessor 712, which cancorrelate that information to the information currently displayed viathe display 722, to determine the nature of user input via the screen.

The display 722 and touch sensor 726 (and possibly one or more keys 730,if included) are the physical elements providing the textual andgraphical user interface for the mobile device 13 b. The microphone 702and speaker 704 may be used as user interface elements for audio inputand output.

The structure and operation of the mobile devices 13 a and 13 b, asoutlined above, were described to by way of example, only.

FIG. 9 illustrates a first exemplary system 900 in which pushcommunication may be implemented. As shown, the system 900 includes themobile device 200 and the MMS server 400, described above in conjunctionwith FIG. 2 and FIG. 4, respectively. A persistent hypertext transferprotocol (HTTP) or hypertext transfer protocol secure (HTTPS) connectionis maintained between the mobile device 200 and the MMS server 400 whileboth the mobile device 200 and the MMS server are online. The mobiledevice 200 may be offline if it is turned off, placed in airplane mode,or taken outside a network coverage area. The MMS server 400 may betaken offline due to damage or maintenance of the MMS server 400. Thepersistent HTTP connection is used to send (e.g., push) outgoing MMSmessages from the mobile device 200 to the MMS server 400 and to send(e.g., push) incoming MMS messages from the MMS server 400 to the mobiledevice 200. Messages are sent (e.g., pushed) between the mobile device200 and the MMS server 400 using the message push link shown in FIG. 9.As shown, the mobile device 200 and the MMS server 400 also sendheartbeat messages to keep the connection alive. The heartbeat messagesmay be sent once every 2 minutes, 4 minutes, 10 minutes, etc., dependingon the load of the mobile device 200 and/or the load of the MMS server400.

FIG. 10 illustrates a second exemplary system 1000 in which pushcommunication may be implemented. As shown, the system 1000 includes ahandset application 1005, a load balancer 1010, a push engine 1015, apush controller 1020, an auth server 1025, a status receiver 1030, amessage feeder 1035, a cache server 1040, a message queue 1045, a statusmessage processor 1050, and a database 1055. The handset application1005 may reside on the mobile device 200. The remaining structures 1010,1015, 1020, 1025, 1030, 1035, 1040, 1045, 1050, and 1055 shown in FIG.10 may reside at the MMS server 400. While a single one of each ofstructure 1005, 1010, 1015, 1020, 1025, 1030, 1035, 1040, 1045, 1050,and 1055 is shown, the system 1000 may be implemented with multiple ofany of these structures. In some examples, two or more of the abovestructures may be combined into a single structure or may reside on thesame machine.

The handset application 1005 is deployed at the mobile device 200. Thehandset application initiates the persistent connection between themobile device 200 and the MMS server 400 (e.g., the load balancer 1010component of the MMS server 400 as shown in FIG. 10). The handsetapplication 1005 maintains the persistent connection using heartbeatmessages. The handset application 1005 receives push MMS messages overthe persistent connection and provides the received messages to otherapplication(s) (e.g., a user interface application) at the mobile device200 for processing.

The push engine 1015 is responsible for accepting the persistentconnection at the MMS server 400 side. The push engine 1015 sendsmessages to the handset application 1005 and receives acknowledgementsfrom the handset application 1005. The load balancer 1010 makes surethat messages are processed in a manner not to overload the mobiledevice 200 or the MMS server 400. For example, a maximum of 1 messageper second, 2 messages per second, etc., may be processed depending onthe processing speeds of the mobile device 200 and the MMS server 400.The remaining messages may be queued for processing by the load balancer1010.

The push controller 1020 is responsible for message routing. In anenvironment with multiple push engines 1015, the push controller 1020stores information regarding which push engine 1015 is associated withwhich mobile device 200. Using this stored information, the pushcontroller 1020 forwards messages received at the MMS server 400 to thecorrect push engine 1015 for further processing.

The auth server 1025 is responsible for authenticating the mobile device200 using the credentials (e.g., mobile device number, subscriberidentity module information, etc.). Once the mobile device 200 isauthenticated, the auth server sends, to the mobile device 200 andthrough the push controller 1020, a unique session identifier (ID) forthe mobile device 200.

The status receiver 1030 is responsible for forwarding thesuccess/failure message status to the messaging queue 1045 from the pushcontroller 1020. The status receiver may be called jreceiver. Themessage feeder 1035 is responsible for receiving message(s) from themessaging queue 1045 and forwarding the received message(s) to the pushcontroller 1020.

The message queue 1045 represents the message queuing system. Themessage queue 1045 stores messages that need to be sent to the mobiledevice 200. Also, the message queue 1045 holds success or failuremessages that need to be processed further. The status message processor1050 processes the success/failure status of messages.

The cache server 1040 caches records of transmitted and receivedmessages in the database 1055 for future access. The database 1055 maystore device information of mobile devices 200 connected to the MMSserver 400 and information about transmitted and received MMS messages.

The following process may be implemented in conjunction with the system1000 of FIG. 10. The handset application 1005 sends the authenticationand connection request to the push engine 1015 with the devicecredentials of the mobile device 200 hosting the handset application.The push engine 1015 forwards the authentication details to the pushcontroller 1020. The push controller 1020 forwards the authenticationdetails to the auth server 1025. After successful validation, the authserver 1025 sends the session ID, the mobile device number, and/or otherregistered application details to the push controller 1020. The pushcontroller forwards the session ID and the other registered applicationdetails to the mobile device 200. After successful authentication, apersistent HTTP or HTTPS connection is maintained between the pushengine 1005 and the handset application 1005 of the mobile device 200.The push engine 1015 sends the heartbeat message to the handsetapplication 1005 to maintain the persistent connection.

The following process for transmitting a message may be implemented inconjunction with the system 1000 of FIG. 10. A message for a particularmobile device 200 is pushed into the message queue 1045. The message maybe an MMS message received from another mobile device. The messagefeeder 1035 pulls the message from the message queue 1035. The messagefeeder 1035 forwards the message to the push controller 1020. The pushcontroller 1020 identifies the correct push engine 1015 based on themobile device number of the destination mobile device 200 and forwardsthe message to that push engine 1015. The push engine 1015 pushes themessage to the handset application 1005 of the mobile device 200.

FIG. 11 is a data flow diagram 1100 of transmitting a multimediamessaging service message using push communication. As shown in FIG. 11,the sender handset application 1110 sends a MMS message, addressed to areceiver mobile device having a receiver handset application 1160, tothe sender push engine 1120. The sender push engine 1120 has apersistent connection with the sender handset application 1110. Thesender push engine 1120 forwards the MMS message to a connected pushcontroller, the sender push controller 1130. The sender push controllerforwards the message to the receiver push controller 1140. The senderpush controller 1130 identifies the receiver push controller 1140 basedon the mobile device number to which the MMS messages is addressed. Thereceiver push controller 1140 forwards the MMS message to the receiverpush engine 1150, which holds the persistent connection to the receivermobile device hosting the receiver handset application 1160. Thereceiver push engine 1150 forwards the MMS message to the receiverhandset application 1160.

After receiving the MMS message, the receiver handset application 1160sends a MMS message acknowledgement to the receiver push engine 1150.The receiver push engine 1150 forwards the acknowledgement to theconnected push controller, which is the receiver push controller 1140.The receiver push controller 1140 forwards the acknowledgement to thesender push controller 1130. The receiver push controller 1140identifies the sender push controller 1130 based on the mobile devicenumber of the sender mobile device. The sender push controller 1130forwards the acknowledgement to the sender push engine 1120. The senderpush engine forwards the acknowledgement to the sender handsetapplication 1110. As a result of this process, the MMS message istransmitted from the sender mobile device to the receiver mobile device,and an acknowledgment is transmitted back to the sender mobile devicefrom the receiver mobile device.

While the foregoing has described what are considered to be the bestmode and/or other examples, it is understood that various modificationsmay be made therein and that the subject matter disclosed herein may beimplemented in various forms and examples, and that the teachings may beapplied in numerous applications, only some of which have been describedherein. It is intended by the following claims to claim any and allapplications, modifications and variations that fall within the truescope of the present teachings.

Unless otherwise stated, all measurements, values, ratings, positions,magnitudes, sizes, and other specifications that are set forth in thisspecification, including in the claims that follow, are approximate, notexact. They are intended to have a reasonable range that is consistentwith the functions to which they relate and with what is customary inthe art to which they pertain.

The scope of protection is limited solely by the claims that now follow.That scope is intended and may be interpreted to be as broad as isconsistent with the ordinary meaning of the language that is used in theclaims when interpreted in light of this specification and theprosecution history that follows and to encompass all structural andfunctional equivalents. Notwithstanding, none of the claims are intendedto embrace subject matter that fails to satisfy the requirement ofSections 101, 102, or 103 of the Patent Act, should may they beinterpreted in such a way. Any unintended embracement of such subjectmatter is hereby disclaimed.

Except as stated immediately above, nothing that has been stated orillustrated is intended or should be interpreted to cause a dedicationof any component, step, feature, object, benefit, advantage, orequivalent to the public, regardless of whether it is or is not recitedin the claims.

It will be understood that the terms and expressions used herein havethe ordinary meaning as is accorded to such terms and expressions withrespect to their corresponding respective areas of inquiry and studyexcept where specific meanings have otherwise been set forth herein.Relational terms such as first and second and the like may be usedsolely to distinguish one entity or action from another withoutnecessarily requiring or implying any actual such relationship or orderbetween such entities or actions. The terms “comprises,” “comprising,”or any other variation thereof, are intended to cover a non-exclusiveinclusion, such that a process, method, article, or apparatus thatcomprises a list of elements does not include only those elements butmay include other elements not expressly listed or inherent to suchprocess, method, article, or apparatus. An element proceeded by “a” or“an” does not, without further constraints, preclude the existence ofadditional identical elements in the process, method, article, orapparatus that comprises the element.

The Abstract of the Disclosure is provided to allow the reader toquickly ascertain the nature of the technical disclosure. It issubmitted with the understanding that it will not be used to interpretor limit the scope or meaning of the claims. In addition, in theforegoing Detailed Description, it can be seen that various features aregrouped together in various embodiments for the purpose of streamliningthe disclosure. This method of disclosure is not to be interpreted asreflecting an intention that the claimed embodiments require morefeatures than are expressly recited in each claim. Rather, as thefollowing claims reflect, inventive subject matter lies in less than allfeatures of a single disclosed embodiment. Thus the following claims arehereby incorporated into the Detailed Description, with each claimstanding on its own as a separately claimed subject matter.

What is claimed is:
 1. A method comprising: presenting, at a touchscreenof a mobile device, a visual user interface comprising a plurality ofthumbnails and a plurality of contact blocks, wherein each thumbnailidentifies a file, and wherein each contact block identifies a contacthaving a messaging address; receiving, via the touchscreen, a selectionof a first thumbnail from the plurality of thumbnails; receiving, viathe touchscreen, an indication of dragging the first thumbnail acrossthe visual user interface to a first contact block; and transmitting,via a messaging server and responsive to the dragging of the firstthumbnail to the first contact block, the file identified in thethumbnail to the messaging address of the contact identified in thefirst contact block, wherein a push connection is established betweenthe mobile device and the messaging server and between the messagingserver and a device associated with the messaging address.
 2. The methodof claim 1, wherein the messaging address comprises a multimediamessaging service (MMS) address, and wherein the file identified in thethumbnail comprises an image file or a video file stored at the mobiledevice.
 3. The method of claim 1, further comprising presenting, withineach contact block, a name of the identified contact.
 4. The method ofclaim 1, wherein the selection of the first thumbnail comprises atouching of the touchscreen at a position corresponding to the firstthumbnail.
 5. The method of claim 1, wherein the plurality of contactblocks are presented adjacent to a first edge of the visual userinterface, and wherein at least a portion of the plurality of thumbnailsare presented adjacent to a second edge of the visual user interface,the second edge being opposite to the first edge.
 6. The method of claim1, wherein the plurality of contact blocks within the visual userinterface correspond to favorite contacts of a user of the mobiledevice.
 7. The method of claim 1, wherein the plurality of contactblocks within the visual user interface correspond to most frequentcontacts of a user of the mobile device.
 8. The method of claim 1,wherein transmitting the file identified in the thumbnail to themessaging address of the first contact identified in the first contactblock comprises: automatically identifying the messaging address; andautomatically and without further input via the touchscreen,transmitting the file identified in the thumbnail to the messagingaddress.
 9. A method comprising: receiving, at a server and from asender mobile device, a message comprising a recipient device addressand a file; attempting to transmit the file to a recipient mobile deviceassociated with the recipient device address, wherein a push connectionis established between the server and the sender mobile device andbetween the server and the recipient mobile device; determining whetheran attempt to transmit the file is successful; if the attempt totransmit the file is successful: receiving, at the server and from therecipient mobile device, an acknowledgement that the file was receivedat the recipient mobile device; deleting, in response to receiving theacknowledgement, the file from a local memory of the server; andtransmitting, to the sender mobile device, an indication that the fileis successfully transmitted to the recipient mobile device; and if theattempt to transmit the file is unsuccessful: reattempting to transmitthe file to the recipient mobile device; and retaining the file in thelocal memory of the server until the file is successfully transmitted tothe recipient mobile device, wherein, upon successful transmission ofthe file to the recipient mobile device, the file is deleted from thelocal memory of the server.
 10. The method of claim 9, wherein therecipient device address comprises a multimedia messaging service (MMS)address, and wherein the file comprises an image file or a video file.11. The method of claim 9, further comprising in response to determiningthat the attempt to transmit the file is unsuccessful, transmitting, tothe sender mobile device, an indication that the attempt to transmit thefile is unsuccessful.
 12. The method of claim 11, further comprising inresponse to determining that the attempt to transmit the file isunsuccessful: determining a failure reason explaining the attempt totransmit the file being unsuccessful; and transmitting, to the sendermobile device, an indication of the failure reason.
 13. The method ofclaim 12, wherein the failure reason includes one or more of therecipient mobile device is offline, the recipient mobile device is busy,or the recipient mobile device lacks memory to store the file.
 14. Themethod of claim 9, wherein attempting to transmit the file to therecipient mobile device associated with the recipient device addresscomprises pushing the file to the recipient device address in real-timeafter receiving, from the sender mobile device, the message comprisingthe recipient device address and the file.
 15. The method of claim 9,further comprising in response to determining that the attempt totransmit the file is unsuccessful, retaining the file in a local memoryof the server until at least one of: the file is successfullytransmitted to the recipient mobile device, a request to cancel theattempt to transmit the file is received from the sender mobile device,or a threshold time period passes after receipt of the message from thesender mobile device.
 16. A mobile device comprising: a touchscreen; oneor more processors; and a memory storing instructions which, whenexecuted by the one or more processors, cause the one or more processorsto: present, at the touchscreen, a visual user interface comprising aplurality of thumbnails and a plurality of contact blocks, wherein eachthumbnail identifies a file, and wherein each contact block identifies acontact having a messaging address; receive, via the touchscreen, aselection of a first thumbnail from the plurality of thumbnails;receive, via the touchscreen, an indication of dragging the firstthumbnail across the visual user interface to a first contact block; andtransmit, via the messaging server and responsive to the dragging of thefirst thumbnail to the first contact block, the file identified in thethumbnail to the messaging address of the contact identified in thefirst contact block, wherein a push connection is established betweenthe mobile device and the messaging server and between the messagingserver and a device associated with the messaging address.
 17. Themobile device of claim 16, wherein the messaging address comprises amultimedia messaging service (MMS) address, and wherein the fileidentified in the thumbnail comprises an image file or a video filestored at the mobile device.
 18. The mobile device of claim 16, thememory further comprising instructions which, when executed by the oneor more processors, cause the one or more processors to present, withineach contact block, a name of the identified contact.
 19. The mobiledevice of claim 16, wherein the selection of the first thumbnailcomprises a touching of the touchscreen at a position corresponding tothe first thumbnail.
 20. The mobile device of claim 16, wherein theplurality of contact blocks are presented adjacent to a first edge ofthe visual user interface, and wherein at least a portion of theplurality of thumbnails are presented adjacent to a second edge of thevisual user interface, the second edge being opposite to the first edge.